System and method for data network reassignment

ABSTRACT

Managing data resource utilization in a wireless network environment comprising a first data network and a second data network is described herein. The described management infrastructure and method incorporates monitoring data usage of a wireless network subscriber over the first data network, determining that the data usage over the first data network meets a specified threshold, and, in response to the determination that usage has reached the specified threshold, administratively disconnecting the wireless network subscriber from the first data network so as to cause a data session of the wireless network subscriber to be reassigned to the second data network.

FIELD OF THE INVENTION

This invention relates generally to the field of wireless communicationsnetworks and associated services. More particularly, the invention isdirected to wireless data communication services (such as thosesupporting data flows to/from smart phones) in such networks, and morespecifically to managing wireless network data resource utilization onan individual user basis in accordance with subscriber agreements.

BACKGROUND OF THE INVENTION

Proliferation of smart phones, and their subsequent use to perform highdata-rate communications, has resulted in an exponential growth in thevolume of data flowing over wireless networks. The increased volume ofdata flowing over the networks is taxing the service providers and thenetwork infrastructure responsible for ensuring the data flows atacceptable rates for most, if not all, users. If unchecked, a smallpopulation of users of the wireless networks, consumers of excessiveportions of the available wireless network bandwidth would degradequality of service for all users. Such abuse of wireless networks, or atleast the threat of such abuse, has led service providers to restrictthe amount of data bits communicated by individual users' wirelessdevices over a specified of period of time (e.g., a month) for a givensubscriber agreement.

A consequence of the phenomenon of greatly expanded data flow, and theresulting imposition of necessary use limits on subscribers that exceedreasonable use limitations based upon their subscription agreement, isthe emergence of large numbers of subscribers that violate, perhapsinnocently, the terms of service of their subscriptions. Identifyingviolators and limiting their data usage is implemented in known systemsby a policy server closely integrated with data transmission within amobile network and potentially introducing unacceptable bottle necks,increased data transmission overhead and delays.

SUMMARY OF THE INVENTION

A method is described for managing data resource utilization in awireless network environment comprising a first data network and asecond data network. The method comprises monitoring data usage over thefirst data network, determining that the data usage over the first datanetwork satisfies a specified criterion. The method further comprises,in response to the determination step, administratively disconnecting awireless network subscriber from the first data network so as to cause adata session of the wireless network subscriber to be reassigned to thesecond data network.

A system is described for managing data resource utilization in awireless network environment. The system comprises a first data network,a second data network communicatively coupled to the first data networkin the wireless network environment, and a rating engine configured tomonitor data usage over the first data network and, upon determiningthat the data usage over the first data network satisfies a specifiedcriterion, cause a wireless network subscriber to be administrativelydisconnected from the first data network so as to further cause a datasession of the wireless network subscriber to be reassigned to thesecond data network.

A non-transitory computer readable medium is described having storedthere on computer executable instructions for managing data resourceutilization in a wireless network environment comprising a first datanetwork and a second data network. The instructions comprisingmonitoring data usage over the first data network, determining that thedata usage over the first data network satisfies a specified criterion.The instructions further comprising, in response to the determinationstep, administratively disconnecting a wireless network subscriber fromthe first data network so as to cause a data session of the wirelessnetwork subscriber to be reassigned to the second data network.

BRIEF DESCRIPTION OF THE DRAWINGS

While the appended claims set forth the features of the presentinvention with particularity, the invention and its advantages are bestunderstood from the following detailed description taken in conjunctionwith the accompanying drawings, of which:

FIG. 1 is a schematic diagram illustrating a mobile environment inaccordance with an embodiment of the invention;

FIG. 2 identifies a set of data fields in a physical storage medium thatsupport management of user data usage and reassignment of users whenlimits are reached in accordance with a subscriber/usage agreement witha data communications service provider; and

FIG. 3 is a schematic diagram illustrating a message flow in accordancewith an embodiment of the invention.

DETAILED DESCRIPTION OF THE DRAWINGS

The following illustrative examples further describe the invention. Theyshould not however, be construed as limiting its scope to any particulardescribed structures or steps.

A system and method are illustratively depicted and described hereinthat reassign a high-speed data mobile device from a relatively higherspeed network (e.g., 1xEVDO) to a lower-speed data network (e.g.,1×RTT). Such reassignment occurs, for example, by way of a network datauser/user management infrastructure including: (a) a back office ratingengine, (b) an Operating Support System (OSS) configured to provisionnetwork elements, and (c) an authentication mechanism for controllingaccess to the high-speed data network. The back office rating engineaccumulates data usage during, for example, a subscriber's monthlybilling cycle. Based on specified criteria (e.g., data usage rulesand/or limits) maintained on the system in accordance with, for example,a subscriber agreement, a threshold for total data usage is set. Afterit has been determined that the subscriber has reached the threshold,the user is reassigned from a current, higher speed, network (e.g.,1xEVDO) to a slower network (e.g., 1×RTT network).

By way of example, after the system determines the subscriber hasreached the threshold, reassignment of the subscriber to the slower datanetwork commences wherein the rating engine triggers the OSS to:administratively disconnect the user from the currently assigned (i.e.,the preferred/higher speed) network by, for example, triggering issuanceof a resource reclaim message from an accounting authenticationauthorization (AAA) server, reclaim network resources previouslyallocated to the subscriber's session including clearing cachedinformation on the session from various network elements such as a radionetwork controller (RNC) and packet data serving node (PDSN), and updatethe AAA user profile to deny A12 device authentication on thepreferred/higher speed network. Thus, at this point the user will beunable to access the preferred/higher speed data network using an IDlinked to the account/subscription for which the data threshold has beenmet. In a particular example (noted above), the user exceeds a datalimit on a preferred network, such as a third generation (3G) 1xEVDOdata network, and is reassigned by the aforementioned system componentsto a slower data network, such as 1×RTT. Thereafter, for eachsubsequently initiated data session (including one initiated by the userin response to being disconnected from the higher speed network) whilethe system registers that the data usage threshold has been met (e.g.,the remainder of a current subscription month), the user will beassigned to the slower network. The subscriber management and networkreassignment scheme does not require integrating a policy server intothe preferred network, and does not require continued use of high-speednetwork resources once a wireless communications subscriber has beenreassigned to a lower speed data network.

There are many ways to implement the reassignment and subsequentre-establishment of permission to use the higher speed data network. Forexample, at the end of the monthly billing cycle, the AAA profile isreset to allow device authentication to continue, thereby again granting3G data network access. Alternatively, in a pay-as-you-go scheme, thesubscriber's rights to use of the higher speed network arere-established upon payment of a specified fee, regardless of whetherthe subscriber's current month has expired. In a hybrid implementationscheme, a user purchases additional data bits on the higher speednetwork and access to the higher speed network continues until thepurchased data bits have been consumed by the user's subsequent use ofthe higher speed network. The above-described alternatives demonstratethe existence of multiple ways for managing a user's/subscriber's statusfor purposes of determining whether the user is reassigned from thehigher speed data network to the lower speed data network.

Turning to FIG. 1, an illustrative schematic diagram depicts anexemplary implementation of a system for implementing theabove-described user reassignment when a data use threshold is reached.The illustrative example is presented in a mobile wireless system 100environment. In the illustrative embodiment, the wireless system 100includes wireless network support structures that operate in accordancewith a CDMA2000 specification. In the exemplary embodiment, the mobilesystem environment incorporates and provides data services supportingmultiple data access protocols, such as 1xEVDO and 1×RTT, thereby havingmultiple data network overlays. In alternative embodiments othermultiple data access protocol combinations are supported within themobile system environment 100. Potentially applicable wireless systemsconcurrently provide multiple data networks, including, withoutlimitation, systems operating in accordance with multiple wirelesscommunications standards, each having its own data access protocol.Examples include embodiments of the wireless system 100 thatconcurrently support multiple data networks performing wirelesstransmissions complying with combinations of multiple wirelesscommunication protocols including generations and/or types oftelecommunication standards, such as LTE, WCDMA, UMTS, GSM, GPRS, EDGE,Wi-Fi (i.e., IEEE 802.11x), WiMAX (i.e., IEEE 802.16), or the like, fordelivering voice and data services to a mobile device 102. The mobiledevice 102 can take on any of a variety of forms including, for example:a mobile phone, a PDA, or a mobile computer (e.g., a laptop, notebook,notepad, tablet, etc.) having wireless data communication capability.

The home location register (HLR) 104 provides services forauthenticating an identity of the mobile device 102 prior to permittingaccess to radio access network resources of the wireless system 100. TheHLR 104, by way of example, maintains a database of subscribers to thewireless system 100. Each individual subscriber (e.g., each distinctlyidentified mobile device) entry includes a Mobile Identification Number(MIN) and/or Electronic Serial Number (ESN).

The wireless system 100 includes a plurality of base stations, such asbase station 106. The base station 106, by way of example, includesradio bearer resources and other transmission equipment necessary forwireless communication of information between the mobile device 102 andother network elements. The number of network overlays delivered by abase station (e.g., base station 106) differs in accordance with variousexemplary network configurations. In the example provided in FIG. 1, thebase station 106 includes radio bearer resources corresponding tomultiple data network overlays. Alternatively, each data network overlayis delivered via a distinct base station.

Moreover, for each data access network, radio access network resourcesare used to control the radio interface aspect of the system 100 thatincludes the plurality of base stations. Control of the radio interfaceof the system 100 is carried out, for example, by a radio networkcontroller (RNC) or a base station controller (BSC), identified in FIG.1 as RNC/BSC 108. The RNC/BSC 108 manages the radio traffic between aplurality of base stations such as base station 106. Such management ofradio traffic includes controlling handoff between sectors and/or basestations.

Additionally, the wireless system 100 illustratively depicted in FIG. 1includes a mobile switching center (MSC) 110. The MSC 110 manages voicecalls placed in and out of the wireless system 100.

Continuing with the illustrative schematic depiction of the wirelessnetwork 100, a packet control function (PCF) 112 is communicativelycoupled to the RNC/BSC 108. The PCF 112 carries out the function ofrouting data packets from the RNC/BSC 108 to one of a set of PDSNs. TheRNC/BSC 108 is, by way of example, collocated with a packet controlfunction (PCF) 112. It is noted that in the illustrative example, thesystem 100 is depicted as having a single packet data serving node(PDSN)—i.e., PDSN 114, and in such instance the PCF 112 is not needed toperform the aforementioned routing to a particular one of multiplePDSNs. However, in cases where a wireless system comprises multiplePDSNs, the PCF 112 selectively routes data packets received from theRNC/BSC 108 to an appropriate one of the set of PDSNs for furtherprocessing.

The illustrative wireless system 100 includes one or more services(implemented in the form of computer executable instructions carried outby processors on one or more physical server machines) that authenticateand determine/designate access rights for particular identified entitiesprior to granting access to the wireless system 100's data networktransmission services. In the exemplary embodiment, such authenticationservices are provided by an accounting authentication authorization(AAA) service 116 and an access node accounting authenticationauthorization (AN-AAA) service 118.

The AAA service 116 carries out the task, during set up of a session foran identified subscriber, of ensuring that the subscriber associatedwith the mobile device 102 is allowed to use the data resources of thesystem 100. After initially confirming the authenticity of theidentified user seeking to establish a user session, the AAA service 116provides a response including a profile for the identified userincluding, among other things, user permissions. The permissions can beimplicit—e.g., the user is identified as belonging to a particulargroup—or explicitly listed in the profile assigned to the system.

In the exemplary system, where multiple, data network overlays aresupported, the AN-AAA service 118 carries out an initial authorizationfunction (e.g., A12 device authentication) to determine whether themobile device 102 is permitted to use a preferred one (e.g., 1xEVDO) ofthe multiple supported data network overlays. By way of example, theRNC/BSC 108 invokes the AN-AAA service 118 prior to setup of a mobile IPsession for the mobile device (via AAA service 116). In response, theAN-AAA service 118 determines whether or not to authorize the mobiledevice 102 for 1xEVDO access. The RNC/BSC 108 communicates with theAN-AAA service 118 using, for example, the RADIUS protocol. It is notedthat the AN-AAA service 118, in accordance with the illustrativeexample, provides an authorization for the mobile device 102 (uponsuccessful authentication/authorization) to establish a session on the1xEVDO data network. The actual creation of such session subsequentlyoccurs via the PDSN 114 and AAA service 116.

Upon completion of the user authorization process for the use of dataresources, via the PDSN 114 and AAA service 116, a home agent (HA) 120forwards an IP address, received from the AAA server 116, to the PDSN114. The PDSN 114, in turn, forwards the IP address to the mobile device102. In the illustrative example, the HA 120 is a router located on ahome network of the mobile device 102. The HA 120 tunnels packets fromthe home network to the mobile device 102 when the mobile device 102 isroaming.

An Operating Support System (OSS) 122 serves as a central point foradministration, management, and provisioning of all network elements.Among other things, the OSS 122 administers the individual accounts ofsubscribers that use the wireless system 100.

In accordance with an exemplary embodiment, the wireless system 100further includes a billing and rating engine 124. As indicated in FIG.1, the billing and rating engine 124 is a back office system that isconfigured to communicate certain information, based upon subscriberusage information received from other components of the system 100, tothe OSS 122. By way of example, the billing and rating engine 124monitors data transmissions (e.g., quantity of data bits transmitted) bywireless network subscribers over the 1xEVDO network overlay (i.e., thepreferred data transmission network). Upon determining that the datausage by a particular subscriber over the high-throughput data networksatisfies a specified criterion (e.g., a specified maximum data usagethreshold, such as 5 GB per billing cycle), the billing and ratingengine 124 issues a notification to the OSS 122 that the subscriber isnot permitted access to the 1xEVDO network. The notification to the OSS122 initiates administrative disconnection of the wireless networksubscriber (e.g., mobile device 102) from the 1xEVDO data network.

“Administratively disconnecting,” as used herein, is intended to bebroadly defined to include a variety of actions taken by networkadministrative components to alter a status of an affected subscriberaccount to prevent users associated with the subscriber account fromusing the data network overlay from which the subscriber account hasbeen administratively disconnected. Thus, act of administrativelydisconnecting a subscriber account, in exemplary embodiments, results inimmediate termination of a current user session. Alternatively,administratively disconnecting a subscriber account does not result inimmediate termination of a current user session. Rather, the currentsession is allowed to persist until a specified future terminating eventoccurs (e.g., the user terminates the current session, a delay timerexpires, a warning has issued and the user failed to respond in asatisfactory manner). Regardless of whether administrativelydisconnecting an account results in immediate termination of a currentsession, in all cases administratively disconnecting an account from ahigher tier data network overlay results in modification of permissionsassigned the subscriber account such that a subsequent request toestablish a session on the higher tier data network, from which theaccount is administratively disconnected, will be denied bylogon/authentication services. For example, as described in furtherdetail in an illustrative example below, the “administrativedisconnection” of a wireless subscriber from the 1xEVDO data networkdoes indeed result in termination of a current session on the 1xEVDOdata network overlay and ensures that a next time the subscriber (e.g.,mobile device 102) attempts to establish a session on the wirelessnetwork, the AN-AAA will reject the subscriber's request to establish asession on the preferred (e.g., 1xEVDO) data network overlay.

It is emphasized that when a particular subscriber is “administrativelydisconnected,” such action by network administration components does notnecessarily terminate a current session. For example, in one example,the subscriber is permitted access to the preferred network overlay forthe remainder of the current session (with a possible “grace period”limit placed on even that session before the violating session isterminated by the system 100). However, regardless of the timing forterminating a current session, the OSS 122 notifies the AN-AAA 118 thata particular “administratively disconnected” subscriber is no longerpermitted access to the preferred (e.g., 1xEVDO) data network overlay,and the AN-AAA 118 denies authorization to the identified subscriber inresponse to an (A12) authentication request received from theadministratively disconnected subscriber via the RNC/BSC 108. Theabove-described administrative disconnection of the subscriber from thepreferred network has the effect of reassigning the wireless networkservice subscriber to a relatively lower-speed (e.g., 1×RTT) datanetwork overlay in the wireless system 100.

As those of ordinary skill in the art will realize, the foregoingnetwork elements of the wireless system 100 are implemented viaspecial-purpose telecommunications equipment having one or more computerprocessors, as well as non-transitory computer readable media, such asRAM/ROM, solid-state memory, and/or hard drive memory and the like,which store computer executable instructions for executing embodimentsof the method described in further detail below with reference to FIG.3.

Turning to FIG. 2, an exemplary set of fields for a data structure areprovided that support management, by the billing and rating engine 124and/or the OSS 122, of subscriber status with regard to permission touse the preferred wireless data network overlay (e.g., 1xEVDO) andreassignment to the lower speed wireless data network overlay (e.g.,1×RTT) by the action of administrative disconnection of a subscriberwhen a data usage threshold is reached for the user. A subscriber_IDfield 150 is a unique value assigned to a particular subscriber (e.g.,the identification assigned to the mobile device 102). In the context ofthe network reassignment scheme described herein, the subscriber_ID 150is the identification assigned to a particular subscriber account (thatmay comprise multiple linked mobile devices—such as multiple deviceslinked to a single account under a “family plan” wireless servicesubscription).

A current data rate plan field 152 identifies one of multiple planssupported by the wireless system 100. An element of the plan of specificinterest, to the billing and rating engine 124, for purposes ofinitiating reassignment and administrative disconnection of a mobiledevice is a monthly allocated monthly data usage limit (e.g., 2gigabytes of data per month) for the subscriber. The data limit,extracted from terms of the identified plan, is stored in a monthly datalimit field 162. For example, if the allocated data usage limit is setto 2 GB of data per month, then the subscriber is administrativelydisconnected, and reassigned from the 1xEVDO data network to the 1×RTTdata network, once data usage specified in field 158 exceeds the 2 GBlimit specified in field 162 (triggering administrative disconnectionand reassignment of the subscriber account).

A monthly recurring charge field 154 stores an amount charged to thewireless customer on a monthly basis for data usage under the planspecified in the current data rate plan field 152. A bill cycle datefield 156 specifies the date of the month in which a subscriber'saccumulated data usage, stored in a monthly accumulated usage field 158,is reset. In the illustrative example, a current usage value countsupward toward a specified limit. However, an alternative, that avoidsrepeated accessing the monthly data limit field 162, is to reset acounter to the monthly data limit every month and subtract from thatstored value (i.e., “data usage remaining”) until the value reaches zeroto signal initiation of “administrative disconnection” and reassignmentof the subscriber to the less preferred wireless data network overlay.

Lastly, a current network assignment field 160 stores a value indicatingthe status of the subscriber with regard to which one, of multiplesupported wireless data network overlays, the subscriber is currentlyassigned. In a case where only two overlays are available (e.g., 1xEVDOand 1×RTT), then a single bit in a record can be used to indicate thecurrent network assignment of the subscriber. In alternativeembodiments, where several networks are available or the availablenetworks changes, alphanumeric strings are used to identify theassignment for a subscriber within the current network assignment field160.

Turning to FIG. 3, a message flow in accordance with an embodiment ofthe invention is shown. In particular, the example is showing a seriesof events and actions that occur when a subscriber's current monthlyaccumulated data usage (see, FIG. 2, field 158) has not yet reached amonthly data limit (see, FIG. 2, field 162). Both of these values are ofcourse maintained by the billing and rating engine 124. In theillustrative example, the monthly accumulated data usage (specified infield 158) for the subscriber account associated with the mobile device102 initially has not reached its monthly limit (specified in field162). During a session the mobile device 102 carries out data transfersover the wireless network causing the account to reach the monthly limit(specified in field 162). The subscriber is administrativelydisconnected from the preferred wireless data network overlay (1xEVDO)and reassigned to the less preferred data network overlay (1×RTT).

Turning to the specific steps depicted in the illustrative example ofFIG. 3, during step 200, the mobile device 102 establishes a datasession over the high-speed data network, such as a third generation(3G) data network, via the RNC 108, AN-AAA 118, and PDSN 114. In anembodiment, the high-speed data network is an 1xEVDO data networkoverlay of the wireless system 100.

In accordance with step 202, during the data session, the PDSN 114communicates the accounting information to the AAA server 116. In theillustrative embodiment, during step 204 the AAA 116, in turn,communicates the accounting information, such as Call Detail Records(CDR), to the billing and rating engine server 124. As previously noted,with reference to FIG. 2, the billing and rating engine 124 maintains arecord describing each subscriber account, data limits (e.g., 5gigabytes per month), and current usage.

Thus, in accordance with step 204, the billing and rating engine 124monitors and accumulates mobile device data usage during the mobiledevice 102's high-speed data session on the preferred wireless networkdata overlay (e.g., 1xEVDO). Upon reaching a data usage thresholdspecified under a current data usage plan that specifies criteria withrespect to the monitored data usage of the preferred wireless datanetwork overlay, the billing and rating engine 124 issues a notificationto the OSS 122 that the subscriber has reached the specified thresholdwhere administrative disconnection and reassignment of the subscriber(to the less preferred data network overlay) occurs. In a particularexample, the billing and rating engine 124 issues a notification to theOSS 122 that the mobile device 102's current session on the preferreddata network overlay should be terminated. In the illustrativeembodiment, the implemented by the billing and rating engine 124comprises a specified data usage limit, such as a maximum allowed datausage over a specified time period (e.g., a billing cycle or dailymaximum usage, or the like), as configured at the OSS 122. In oneembodiment, the specified data usage limit for the high-speed datanetwork is applicable to the roaming subscribers in order to prioritizethe high-speed data network resources for the home subscriberpopulation. Alternatively, the above reassignment and administrativedisconnection functionality is coupled with a tiered pricing scheme.Thus, in this alternative embodiment, after a subscriber account reachesa threshold specified by the monthly data limit, rather than precludingthe user from using the preferred data network overlay, the subscriberis permitted to consent to being charged a premium to continue access onthe preferred wireless data network overlay. If the subscriber does notconsent to payment of the premium, the subscriber is reassigned to theless preferred (e.g., 1×RTT) data network overlay for the remainder ofthe billing cycle. It is noted that the above decision-making occurs inthe OSS 122, rather than the billing and rating engine 124, in otherimplementations of the administrative disconnection and reassignmentscheme generally described herein wherein subscribers are precluded fromusing a preferred data network overlay when their usage meets aspecified threshold.

Thus, in accordance with the above-described exemplary usage monitoringand plan data limit enforcement functionality, during step 206 thebilling and rating engine 124 sends a Terminate and Redirect message tothe OSS 122. The Terminate and Redirect message can take on any of avariety of forms depending on the preferences of the OSS 122'sparticular vender preferences. In a simple case, a web services APIexposed by the OSS (and invoked by a call from the billing and ratingengine 124) would implement the Terminate and Redirect message causingthe mobile device 102 session to be terminated. In other instances lessdrastic measures are taken such as the user is notified that thesubscription has been reassigned to the less preferred data networkoverlay (i.e., the current session will not terminate and reassignmentwill take effect the next time the subscriber attempts to connect to thewireless network).

In accordance with an illustrative example, receipt of the Terminate andRedirect message causes the OSS 122 to initiate a plurality of messagesfor disconnecting the mobile device 102 from the high-speed datanetwork, clearing all cached session information from various networkelements (e.g., from the RNC, AN-AAA, and PDSN), and updating the userprofile at the AAA server 116 to deny A12 device authentication on thehigh-speed data network.

Specifically, as illustratively depicted in steps 208-210, the OSS 122sends a Resource Reclaim message to the AAA 116 and updates the userprofile at the AN-AAA server 118 to indicate that any subsequent A12authentication request from the mobile device 102 to the AN-AAA server118 for permission to establish a session on the high-speed data networkshould be denied. In the illustrative example, the OSS 122 instructs theAN-AAA server 118 to deny authentication. Such instruction will remainin place at the AN-AAA server 118 until the OSS 122 rescinds thedirective to deny access by the mobile device 102's subscriber to thepreferred wireless data network overlay. The subsequent instruction torescind the denial directive is issued, possibly on a scheduled basis,upon commencement of a next billing cycle or any other specified timeperiod.

With continued reference to the illustrative example in FIG. 3, duringstep 212 the OSS 122 sends a message to the RNC 108 to disconnect thecurrent session of the mobile device 102 on the preferred data networkoverlay. The RNC 108 then clears a session cache timer for thehigh-speed data session so that the mobile device 102 is no longerauthenticated. Moreover, in response to receiving (during step 108) theResource Reclaim message from the OSS 122, during step 214 the AAAserver 116 issues a Resource Reclaim Request message to the HA 120. Atstep 215, the HA 120 thereafter terminates the high-speed data sessionfor the mobile device 102. Thereafter, at step 216 the HA 120 issues aResource Reclaim Response message to the AAA server 116.

Consequently, at a later time when the mobile device 102 issues arequest to establish a session on the preferred wireless data networkoverlay (e.g., the 1xEVDO overlay), the A12 authentication request isdenied by the AN-AAA 118. This request/denial sequence is depicted insteps 218 and 220 of FIG. 3. In the illustrative example, upon denial ofthe request to establish a session on the preferred wireless datanetwork overlay, the mobile device 102 automatically (or manually by theuser) issues a request to initiate a session on the less preferred(e.g., 1×RTT) wireless data network overlay, based on mobile devicesettings.

In another embodiment, the mobile device 102 is directed by the wirelesssystem 100 (e.g., by OSS 122) to initiate the data session on thelow-speed 1×RTT network. Such functionality is implemented, for example,using an application that controls the communication stack of the mobiledevice 102. The application communicates directly with the OSS(client-server model) via a well know protocol such as “http over port80.” Once the mobile device 102 is informed that access to the 1xEVDOdata network overlay will not be granted, the application will commenceinitiation of a 1×RTT wireless data session.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the invention (especially in the context of thefollowing claims) are to be construed to cover both the singular and theplural, unless otherwise indicated herein or clearly contradicted bycontext. The terms “comprising,” “having,” “including,” and “containing”are to be construed as open-ended terms (i.e., meaning “including, butnot limited to,”) unless otherwise noted. Recitation of ranges of valuesherein are merely intended to serve as a shorthand method of referringindividually to each distinct value falling within the range, unlessotherwise indicated herein, and each distinct value is incorporated intothe specification as if it were individually recited herein. All methodsdescribed herein can be performed in any suitable order unless otherwiseindicated herein or otherwise clearly contradicted by context. The useof any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate the inventionand does not pose a limitation on the scope of the invention unlessotherwise claimed. No language in the specification should be construedas indicating any non-claimed element as essential to the practice ofthe invention.

Preferred embodiments of this invention are described herein, includingthe best mode known to the inventors for carrying out the invention.Variations of those preferred embodiments may become apparent to thoseof ordinary skill in the art upon reading the foregoing description. Theinventors expect skilled artisans to employ such variations asappropriate, and the inventors intend for the invention to be practicedotherwise than as specifically described herein. Accordingly, thisinvention includes all modifications and equivalents of the subjectmatter recited in the claims appended hereto as permitted by applicablelaw. Moreover, any combination of the above-described elements in allpossible variations thereof is encompassed by the invention unlessotherwise indicated herein or otherwise clearly contradicted by context.

1. A method for managing data resource utilization in a wireless networkenvironment comprising a first data network and a second data network,the method comprising: monitoring data usage over the first datanetwork; determining that the data usage over the first data networksatisfies a specified criterion; and in response to the determiningstep, administratively disconnecting a wireless network subscriber fromthe first data network so as to cause a subsequent data session of thewireless network subscriber to be reassigned to the second data network.2. The method of claim 1 wherein the data usage over the first datanetwork measured during the monitoring step is data usage by thewireless network subscriber.
 3. The method of claim 2 wherein thespecified criterion comprises reaching a specified maximum usagethreshold by the wireless network subscriber.
 4. The method of claim 3wherein the maximum usage threshold is associated with a specifiedduration.
 5. The method of claim 4 wherein the wireless networksubscriber is prevented from establishing a session on the first datanetwork for a remainder of the specified duration.
 6. The method ofclaim 2 wherein the first data network is configured to support a higherdata throughput per user session than a throughput supported on a peruser session on the second data network.
 7. The method of claim 2wherein administratively disconnecting the wireless network subscriberfrom the first data network comprises triggering a resource reclaimmessage.
 8. The method of claim 2 wherein, as a consequence ofadministratively disconnecting the wireless network subscriber, furthersteps are performed for: clearing cached information on the data sessionfrom a plurality of network elements, and updating a user profileassociated with the wireless network subscriber to deny user deviceauthentication on the first data network.
 9. The method of claim 8wherein the plurality of network elements comprises at least one of aRadio Network Controller (RNC) and a Packet Data Serving Node (PDSN).10. The method of claim 8 wherein after the user device is deniedauthentication on the first data network, further steps are performed toautomatically route a request to initiate a data session to the seconddata network.
 11. The method of claim 6 further comprising: denying, inaccordance with the administratively disconnecting, the user deviceauthentication on the first data network, and directing, after thedenying step, a request to initiate a data session by the user device tothe second data network.
 12. A system for managing data resourceutilization in a wireless network environment, the system comprising: afirst data network; a second data network communicatively coupled to thefirst data network in the wireless network environment; and a ratingengine configured to monitor data usage over the first data network and,upon determining that the data usage over the first data networksatisfies a specified criterion, cause a wireless network subscriber tobe administratively disconnected from the first data network so as tofurther cause a subsequent data session of the wireless networksubscriber to be reassigned to the second data network.
 13. The systemof claim 12 wherein the data usage over the first data network monitoredby the rating engine is data usage by the wireless network subscriber.14. The system of claim 13 wherein the specified criterion comprisesreaching a predetermined maximum usage threshold by the wireless networksubscriber.
 15. The system of claim 14 wherein the maximum usagethreshold is associated with a specified duration.
 16. The system ofclaim 15 wherein the wireless network subscriber is prevented fromestablishing a session on the first data network for a remainder of thespecified duration.
 17. The system of claim 13 wherein the first datanetwork is configured to support a higher data throughput per usersession than a throughput supported on a per user session on the seconddata network.
 18. The system of claim 13 wherein the rating enginecauses the wireless network subscriber to be administrativelydisconnected from the first data network by causing an Operation andSupport System (OSS) to trigger a resource reclaim message.
 19. Thesystem of claim 13 wherein, as a consequence of the administrativedisconnection of the wireless network subscriber, the rating enginecauses the Operation and Support System (OSS) to clear cachedinformation on the data session from a plurality of network elements andto update a user profile associated with the wireless network subscriberto deny user device authentication on the first data network.
 20. Thesystem of claim 19 wherein the plurality of network elements comprisesat least one of a Radio Network Controller (RNC) and a Packet DataServing Node (PDSN). 21-33. (canceled)